Collect all l10n fallback strings, used in the viewer, in one helper function (PR 12981 follow-up) #13050
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rather than having to spell out the English fallback strings at every single
IL10n.get
call-site throughout the viewer, we can simplify things by collecting them in one central spot.This provides a much better overview of the fallback l10n strings used, which makes future changes easier and ensures that fallback strings occuring in multiple places cannot accidentally get out of sync.
Furthermore, by making the
fallback
parameter of theIL10n.get
method optional[1] many of the call-sites (and their surrounding code) become a lot less verbose.[1] It's obviously still possible to pass in a fallback string, it's just not required.